Structured text for electronic communications

ABSTRACT

Various aspects disclosed relate to a method of creating a manifest record for an outgoing electronic communication. The method includes identifying at least one document to be sent with the outgoing electronic communication, receiving a message comprising unstructured text to be inserted into the outgoing electronic communication, generating a manifest record for attachment to the outgoing electronic communication, attaching the at least one document and the manifest record to the outgoing electronic communication, and sending the outgoing electronic communication with the document and the manifest record attached. The manifest record includes structured data specifying the document type and the message type, wherein generating the manifest record includes assigning the message type associated with the message and the document type associated with the at least one document to the manifest record.

CLAIM OF PRIORITY

This application claims the benefit of priority under 35 U.S.C. § 119(e)to U.S. Patent Application Ser. No. 62/935,566, filed on Nov. 14, 2019,which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The application is directed to electronic communications, and morespecifically to structured text for e-mail communications.

BACKGROUND

Electronic communication, such as e-mail or SMS text messaging, isubiquitously used throughout business and personal functions on a dailybasis to communicate about various events, tasks, due dates, and otherinformation. Electronic communication functions across computernetworks, including the internet, such that users all over the globe maycommunicate instantly.

Each user of electronic communication uses a different computing programand user interface for electronic communication. Moreover, the text inthe body of electronic communication is free form, and oftenunstructured. For this reason, a received electronic communicationtypically must be read by a human user and interpreted before anyfunction or action is subsequently taken based on the contents of theelectronic communication.

SUMMARY

The systems and methods described herein address the needs in the art byproviding methods of creating structured text for inclusion inelectronic communications to enable automated, computer executed actionsbased on the information in that structured text, without need foradditional human interpretation of the structured text.

Discussed herein is a manifest record generating program. A manifestrecord may include structured text describing certain qualities of anelectronic communication, such as the type of message, type of attacheddocuments, and associated deadlines. The structured text may be read bya computing program and induce automated actions and/or responses to themanifest record in a computing system, such as an update to filedatabases, notifications of required responses, or updated deadlines.

In a first aspect, a method of creating a manifest record for anoutgoing electronic communication includes receiving a message havingunstructured text to be inserted into the outgoing electroniccommunication, generating a manifest record for attachment to theoutgoing electronic communication, the manifest record includingstructured data specifying a message type, wherein generating themanifest record comprises assigning the message type associated with themessage, attaching the manifest record to the outgoing electroniccommunication, and sending the outgoing electronic communication withthe manifest record.

In a second aspect, a method includes receiving an electroniccommunication having unstructured text in a body of the electroniccommunication, and a manifest record that specifies a message typeassociated with the electronic communication, saving a copy of themanifest record, reading the manifest record to determine the messagetype, and executing an action in an electronic system automaticallybased on the manifest record.

In a third aspect, a non-transitory computer-readable medium storesinstructions that when executed by one or more processors cause the oneor more processors to perform operations including receiving a messageincluding unstructured text to be inserted into an outgoing electroniccommunication, generating a manifest record for attachment to theoutgoing electronic communication, the manifest record includingstructured data specifying a message type, wherein generating themanifest record comprises assigning the message type associated with themessage to the manifest record, attaching the manifest record to theoutgoing electronic communication, and sending the outgoing electroniccommunication with the manifest record attached.

In a fourth aspect, a non-transitory computer-readable medium storesinstructions that when executed by one or more processors cause the oneor more processors to perform operations including receiving anelectronic communication having unstructured text in a body of theelectronic communication and a manifest record specifying a message typeassociated with the electronic communication, saving a copy of themanifest record, reading the manifest record to determine the messagetype, and executing an action in an electronic system automaticallybased on the manifest record.

In a fifth aspect, a system includes a manifest record creation systemthat creates a manifest record including structured text describing anaction to be executed by a computing machine upon receipt of anassociated electronic communication, and an electronic communicationsystem that produces an electronic communication, attaches the manifestrecord to the electronic communication, and sends the electroniccommunication to a recipient.

In a sixth aspect, a system includes an electronic communication systemthat receives an electronic communication with manifest record attached,the manifest record including structured text describing an action to betaken upon receipt of the electronic communication, and an automateddocketing system that interprets the structured text in the manifestrecord and executes the action.

In some embodiments, the disclosed method provides a mechanism to allowexecution of automated actions in an electronic system based onstructured text included with an electronic communication.

In some embodiments, the disclosed method provides a mechanism for anelectronic communication user to produce structured text to include withtheir electronic communication, regardless of the server, application,program, or user interface from which the electronic communicationoriginates.

In some embodiments, the disclosed method provides a mechanism for anelectronic communication user to receive an electronic communicationincluding structured text and to automatically execute an action in anelectronic system based on the structured text.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a block diagram depicting a file management system.

FIGS. 2A-2B depict diagrams of a manifest record and associatedelectronic message.

FIG. 2C depicts a schematic diagram of an electronic communicationsystem sending manifest records to a docketing system.

FIG. 3 is a flow chart of a manifest record generating program creatinga manifest record in various embodiments.

FIG. 4 is a flow chart of the manifest record from FIG. 3 being receivedand an action being executed based on the manifest record in variousembodiments.

FIG. 5 is a flow chart depicting the use of a manifest record generatingprogram in a predictive manner in various embodiments.

FIG. 6 is a flow chart of a manifest record generating program creatinga manifest record for an outside organization action in variousembodiments.

FIG. 7 is a flow chart of a manifest record generating program creatinga manifest record for an internal action reporting to the outsideorganization in various embodiments.

FIG. 8 is a flow chart of a manifest record generating program creatinga manifest record for an action by a third party in various embodiments.

FIG. 9 is a flow chart of a manifest record generating program creatinga manifest record for an internal action reporting to a third party invarious embodiments.

FIG. 10 is a schematic of a user interface for any of the manifestrecord generating programs of FIGS. 3-9 in various embodiments.

FIG. 11 is a block diagram of a typical, general-purpose computer thatmay be programmed into a special purpose computer suitable forimplementing one or more embodiments of the manifest record generatingprogram disclosed herein.

DESCRIPTION

The following description with respect to FIGS. 1-11 sufficientlyillustrates specific embodiments to enable those skilled in the art topractice them. Other embodiments may incorporate structural, logical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

Terminology

As used herein, “electronic communication” refers to an electronicmessage or a method of exchanging messages between people usingelectronic devices.

As used herein, “unstructured text” or “unstructured data” refers todata that is not organized in a standard format, for example, text inthe body of an electronic communication.

As used herein, “structured text” or “structured data” refers to datathat is organized in a standard format such that a recipient may readthe data and institute an automated computing system action withouthuman interpretation of the data.

As used herein, “manifest record” refers to structured electronic textor data that is in a standardized format and readable using electronicmeans and that identifies the content of an associated electroniccommunication.

Overview

Electronic communication is used extensively to communicate, often withincluded attachments, such as documents. The body of electroniccommunication messages generally includes unstructured text or data. Todiscern the electronic communication message purpose and type ofattachment, a human user typically must read the unstructured text ordata within the e-mail.

The use of unstructured text or data in e-mails prevents automatedactions based on the incoming electronic communication. For example, acomputer executed action or software program may respond to the incominge-mail only after the unstructured text is interpreted.

In contrast, if structured data, such as an annotation or manifestrecord, is included with the electronic communication, an action may beautomatically executed based on the structured data in the manifestrecord.

Disclosed herein, in various embodiments, is a manifest recordgenerating program and a method of creating structured data (“manifestrecords”) for attachment to electronic communication in coordinationwith at least one document. The program has at least two informationfields, one for categorizing the type of message being sent in theelectronic communication; the other for categorizing the type ofdocument being attached to the electronic communication. The manifestrecord generating program may be locally run and save manifest recordsto a local security environment.

In some embodiments, when the manifest record generating program isused, it generates structured data based on the two information fields,and optionally additional fields. The structured data may be attached toor included in the message of the electronic communication so that therecipient of the electronic communication may read the structured dataand automate electronic communication (and attached document) sorting,docketing, or other business purposes, without requiring a human to readthe unstructured data in the electronic communication body.

The manifest record generating program may optionally aggregate manifestrecords and review previous manifest records for a particularfile/project upon the creation of a new manifest record. This allows themanifest record generating program to predict what manifest recordshould be generated next.

Document Management System

FIG. 1 is a block diagram depicting a manifest record creation system100 for creating one or more manifest records. Manifest record creationsystem 100 may include work sources 110, file management system 120, andworkflow 130. Work sources may include internal sources 112, externalorganization sources 114, and/or third-party sources 116.

In an office or company handling large number of projects, the companyoften relies on some sort of document management system. The documentmanagement system may coordinate incoming data and/or documents througha file management system 120 to indicate to the office what workflow(e.g., tasks, responses, or specific steps) may need to occur inresponse to those documents and/or data in a given project.

For example, the office may be working on a particular “Project A” whichinvolves the office working back and forth with an external organizationfor a particular work product. For “Project A,” there may be a series ofdeadlines that must be met by the office while interacting with theexternal organization. These may include, for example, responsedeadlines, due dates for documents, required meetings or discussions,and other tasks or items related to Project A.

The series of deadlines in Project A may be provided to the office bythe external organization in documents and/or communications sent fromthe external organization to the office. Alternatively, the officeitself may internally provide documents and/or communications withdeadlines or tasks. Additionally, third parties may provide documentsand/or communications with deadlines or tasks related to Project A. Totrack these deadlines for Project A, and any associated documents orfiles, the office may use manifest record creation system 100.

Manifest record creation system 100 may intake incoming documents anddata from work sources 110 from the external organization, internally,or from third parties, into a file management system 120, and produce aworkflow 130 for the office.

Incoming sources of data and documents may include internal sources 112,external organization sources 114, and third-party sources 116. Internalsources 112 of data and documents may include, for example, employeecreated deadlines or meeting dates, or reminders for upcoming deadlinesassociated with the external organization.

External organization sources 114 may include, for example,communications from the external organization, such as incoming e-mailmessages, paper mail, or phone calls. The external organization sources114 may potentially include documents associated with the Project A,such as written documents or spreadsheets with relevant information. Theexternal organization sources 114 may potentially include deadlines ordue dates for response to the external organization.

Third-party sources 116 may include, for example, communications from athird-party business or organization working in conjunction with theoffice on Project A. For example, the third-party may be a foreignoffice working on parts of Project A relevant to their residency.Third-party sources 116 of incoming information may includecommunications such as telephone calls, paper mail, e-mail, or otherforms of communication. Like the other sources of information,third-party sources 116 may potentially include documents and/ordeadlines and due dates for response to the third party and/or theexternal organization.

The file management system 120 may receive data and documents from anyand/or all of these sources 112, 114, 116. Incoming sources of data anddocuments may induce one or more actions that may be taken within theoffice. File management system 120 may be a partially or whollyautomated system for synthesizing incoming data and documents. Filemanagement system 120 may receive and analyze incoming documents or datafrom sources 112, 114, 116.

Based on the information from those sources, file management system 120may produce a task list, a calendar of deadlines, and/or a system ofreminders encompassed in workflow 130. The file management system 120may synthesize the incoming data and documents, and associated actionsto produce workflow 130, which may indicate to the office what should bedone in Project A and by which due date(s).

The workflow 130 may, for example, be a list, calendar, or othertracking system showing tasks and deadlines associated with Project A.For example, if a document including a response deadline is receivedfrom the external organization (e.g., source 114) to file managementsystem 120, the file management system 120 may recognize the responsedeadline and add it to workflow 130.

In this case, manifest record creation system 100 may allow for trackingand upkeep of a large number of projects, and their associateddeadlines, documents, and tasks for an office. Where file managementsystem 120 is automated, the file management system 120 may operate moreefficiently than partially or non-automated systems.

Manifest Record

In manifest record creation system 100, structured text may allow forautomated management of incoming data from various sources. Structuredtext may include data that may be interpreted by a computing program(e.g., an automated filing system), such that the computing program mayexecute one or more actions based on the data in the structured text.For example, the computing program may interpret the structured text andidentify the associated project, file away associated documents, and/orschedule a deadline based on that structured text.

An example of structured text may include a “manifest record,” designedto describe facts associated with an incoming document. FIG. 2A is anexample of a manifest record 200 created by a manifest record generatingprogram, such as the manifest record generating program as described inreference to FIG. 3 below.

Manifest record 200 may include structured text 202 that indicatesvarious properties of an associated message (e.g., an e-mail, textmessage, or other electronic communication). In FIG. 2B, structured text202 includes text describing the type of message, the type of documentattached to the electronic communication, and the upcoming deadlineassociated with that message. Manifest record 200 may be text that isembedded in an electronic communication or attached to it.

Manifest record 200 may include structure text describing a project nameor file number, the type of message, the type of document(s) attached orincluding with the message, deadlines that require response or action,and other information specific to the message. Manifest record 200structured text may be read by a computing program, such as an automatedfile management system, to allow creation of tasks or a workflow withoutinterpretation of unstructured text in the body of the electroniccommunication.

FIG. 2B shows a diagram of an example electronic communication with anembedded manifest record 200. In some examples, the electroniccommunication may be an e-mail, a text message, or other type ofmessage. In FIG. 2B, the communication is e-mail 250. E-mail 250includes recipient fields 252, 254, title field 256, message body field258 and manifest record 200. The fields 252, 254, 256, 258, may befilled out as normal. In some cases, relevant documents may be attachedto the e-mail.

In some examples, the manifest record 200 may be attached to the e-mailinstead of embedded. In this case, the manifest record 200 may take theform of a spreadsheet, a comma separate values (CSV) format file, orother appropriate attachment format.

Whether the manifest record 200 is embedded in the message body field258 or attached, the manifest record 200 may contain structured dataindicating to the recipient what the message is about, which file themessage is associated with, what the nature of any attached documentsare, and whether there are any upcoming due dates associated with theelectronic communication.

FIG. 2C depicts manifest record creation system 100 working with anelectronic communication system 260 to create an electroniccommunication 250 with a manifest record 200, and send thatcommunication to a docketing system 270, which in turn updates a file ina database 280.

In FIG. 2C, the manifest record creation system 100 may work asdiscussed above with reference to FIGS. 1, 2A, and 2B. Manifest recordcreation system 100 may intake documents and data and create a manifestrecord 200 that may be incorporated into an electronic communication 250in conjunction with an electronic communication system 260, such as ane-mail server. Manifest record 200 may include structured data regardingthe documents and data taken in by manifest record creation system 100.

The electronic communication system 260 may send the produced electroniccommunication 250 with attached manifest record 200 to a projectmanagement system such as docketing system 270. Docketing system 270 maybe automated or partially automated. In general, docketing system 270may receive and interpret incoming documents, communications, and data.Docketing system 270 may read and review these incoming items and updatea specific project file accordingly.

Here, where electronic communication system 260 sends an electroniccommunication 250 with an attached manifest record 200, the docketingsystem 270 may receive and interpret the manifest record 200. Becausemanifest record 200 has structured text describing the message type,document type, and/or associated deadlines, the automated (or partiallyautomated) docketing system 270 may interpret that structured textautomatically. Based on the information described in the structuredtext, the docketing system may, for example, update the project filewith a new upcoming deadline.

Manifest Record Generating Program

The examples of FIGS. 3 to 10 discuss the use of a manifest recordgenerating program in the context of a law firm docketing system.However, alternative uses of the manifest record generating program areenvisioned, such as use in tracking sales and marketing projects,financial analysis, engineering developments, mergers and acquisitions,litigation cases, general law practice, and a variety of otherapplications.

FIG. 3 is a flow chart of an example manifest record generating programthat implements a method 300 for creating a manifest record. In method300, a manifest record generating program (e.g. manifest record creationsystem 100 discussed with reference to FIGS. 1 and 2A-2C) may create amanifest record 200 for sending with an electronic communication 250through an electronic communication system 260.

Method 300 may be used, for example, in the context of a patent lawdocketing system. In such a docketing system, a large volume of patentcases may be open simultaneously. Each case has its own set of dueand/or response dates for particular tasks that should be accomplishedby the patent law office. Because each case is generally opened ondiffering dates, the due and/or response dates for each case alsodiffer, creating a complex number of due and/or response dates to trackin a law firm setting. Thus, a docketing system may be used to track therelevant dates and associated tasks.

For example, each case filed with the U.S. Patent Office (USPTO) or aforeign patent office has a list of due dates for action that should notbe missed, such as priority dates, filing dates, responses to officeaction or search reports, due dates for the paying of maintenance fees,and a plethora of other types of response dates.

In general, messages associated with a particular patent case also havea specific purpose. For example, the message could be reporting that apatent application was filed on a particular date, or requestinginstructions from the attorney who drafted the patent. In other cases,the messages may be received directly from a patent office responding toa patent filing.

Additionally, many electronic communications regarding patent casesrequire response or action on the part of the law firm receiving thosecommunications. For example, a law firm could receive a communicationfrom the USPTO indicating an office action was issued in the patent casefrom the examiner, include the attached document, and require a responsewithin a 6-month timeline, with various shorter deadlines built intothat 6-month timeframe.

A docketing system receiving such an electronic communication would berequired to receive the message, interpret the subject of the message(an office action), and associate the deadline (6 months), recording atask (the response) that needed to accomplished by that deadline.

In the past, a user would be required to read unstructured text in thebody of the electronic communication to gather these pieces ofinformation, and manually enter them into a docket (e.g., a calendar ofevents for the patent case).

With method 300, structured text, such as a produced manifest record,may allow a computing program to receive the electronic communicationand automatically identify the subject of the message, deadline, andassociated task. The computing program could automatically docket therequire response and deadline based on this information withoutrequiring manual interpretation of the unstructured body of theelectronic communication.

In method 300, the manifest record generating program first receivesinformation for a new electronic communication to be sent out (step310). This information may include recipient name and/or address, carboncopy (CC) or blind carbon copy (BCC) recipients and/or addresses, andother information, such as a subject, date, or other fields. Theelectronic communication may include, for example, fields such as asender field, a recipient field, a subject field, and a body field. Theelectronic communication may be, for example, an e-mail, an SMS or MMStext message, an app-based messaging service, a voice-to-textcommunication, or other electronic communication.

Next, the manifest generating program receives unstructured text (step320). Unstructured text may include, for example, a message from thesender to the recipient in the body of the electronic communication. Theunstructured data may include, for example, a greeting, a date reminder,an explanation of the purpose of the electronic communication, one ormore questions, or other message items.

Subsequently, the manifest record generating program creates a manifestrecord based on the received information (step 330). The manifest recordis structured data that may be attached to or included in the body ofthe electronic communication. The manifest record specifies, forexample, the type of message in the electronic communication andoptionally a type of document attached to the electronic communicationin addition to associated due date(s).

The manifest record may specify message type for the electroniccommunication. The manifest record generating program may assign amessage type by receiving a user-selected input from a first menu. Themanifest record generating program may display the first menu as adrop-down menu, a drag and drop field, a pop-up menu, or alternativeappropriate menu type.

The message type may specify a topic for the electronic communication.For example, the message type may denote the type of task that may berequired based on the electronic communication content. In the contextof a patent docketing system, the message type may be, for example,reporting an issued search report, reporting a filing activity,requesting instructions from patent counsel, or other types of tasksthat may be associated with that particular case.

The message type of the electronic communication, (e.g., the topic orpurpose for the message), may, for example, include a title, such as“office action received” or “instructions due.”

In addition, the manifest record generating program may assignbibliographic information to the manifest record, such as docketnumbers, due dates, and names of parties involved. In a patent law case,the bibliographic information may include, for example, the patentoffice application number, publication number, inventor(s), assignee(s),priority date, filing date, and/or docket number(s).

The manifest record generating program may receive this type ofbibliographic information through an additional menu (or set of menus),such as drop-down menus, or alternative a set of fields for user inputin a user interface. The manifest record generating program may inputthis bibliographic information to the manifest record, when generated,as structured text.

The manifest record may also specify a document type where an attachmentis included with the electronic communication. The document type mayspecify a type of form or written communication for the attachment. Inthe context of a patent docketing system, the document type may be, forexample, a patent office notice, search report, or office action, a setof instructions or draft response, an analysis of the case, a replybrief or other opinion, or other types of documents.

The manifest record generating program may assign a document type byreceiving input from a second menu. In the second menu, the manifestrecord generating program may display several choices. The manifestrecord generating program may display the second menu as a drop-downmenu, a drag and drop field, a pop-up menu, or alternative appropriatemenu type. The manifest record generating program may change the choicesavailable in the second menu based on the assigned message type receivedfrom the first menu.

The manifest record itself may be an electronic document, such as a worddocument, text file, rich text file, word processor file, excel or otherspreadsheet, or comma-separated values (CSV) format file created by themanifest record generating program. The manifest record generatingprogram may include structured text relating to the electroniccommunication or attachment in the manifest record.

The manifest record generating program may include additional structuredtext in the manifest record. For example, the manifest record generatingprogram may include structured text in the manifest record related todue date, response date, report information, event information, e-mailpurpose, additional attachments, or combinations thereof.

The manifest record generating program may optionally store the manifestrecord in a local security environment. For example, the manifest recordgenerating program may store the manifest record in a network containedwithin a firewall, or alternatively on a local drive or computer. Themanifest record generating program may, for example, save a copy of themanifest record in a folder on a computer directory.

Optionally, the manifest record generating program may aggregatemanifest records for a given file, project, or case. In this case, themanifest record generating program may save copies of manifest recordsrelated to that specific file, project, or case, in a centralizedlocation, such that the manifest record generating program may be ableto review the aggregated manifest records at a later time. Theaggregated manifest records may potentially inform the manifest recordgenerating program in the creation of new manifest records. This featureis discussed in more detail with reference to FIG. 5 below.

After the manifest record generating program creates the manifestrecord, the manifest record generating program attaches the manifestrecord to the electronic communication (step 340). In some cases, theprogram may attach the manifest record as comma separated values, text,or a spreadsheet file to the electronic communication (see, e.g., FIGS.2A-2B). Alternatively, the program may generate the manifest record forembedding in the electronic communication. For example, the program maygenerate the manifest record as copy-able structured text that may becopied and pasted into a message body field of an electroniccommunication. Alternatively, the manifest record generating program mayproduce an electronic communication with the manifest record already inor attached to the electronic communication.

The manifest record generating program may additionally receive andattach associated document(s) to the electronic communication, inaddition to creating and attaching/embedding the manifest recorddescribing the message and document types. In step 350, the manifestrecord generating program may receive one or more documents forattachment. This may be done by displaying a drag and drop field, oranother document receiving field. Optionally, an additional field forthe document name(s) may be displayed on a user interface so that themanifest record generating program may associate a name with eachdocument. The program may attach document(s) to the electroniccommunication before or after creating the manifest record, and beforeor after attaching/embedding the manifest record to the electroniccommunication. The attached document(s) may be associated with thedocument type(s) described in the structured text of the producedmanifest record.

Subsequently, the manifest record generating program sends theelectronic communication (step 360) to the recipient. In some cases, theprogram may prepare the electronic communication and allow for review ofthe electronic communication with manifest record by a user. Afterconfirmation from a user, the manifest record generation program maysend the electronic communication with manifest record. Alternatively,the program may generate the electronic communication with manifestrecord, which may be sent manually. In still another example, theprogram may generate just the manifest record, which may be manuallyincorporated into an electronic communication. The receipt of theelectronic communication with attached manifest record is discussed withreference to FIG. 4 below.

FIG. 4 is a method 400 of receiving and interpreting a manifest recordmade by the manifest record generating program described with referenceto FIG. 3 above. In method 400, a computing system, such as, forexample, a patent docketing system, receives the manifest record andexecutes one or more actions based on that manifest record. In method400, a computing system (e.g., automated or semi-automated docketingsystem 270 discussed with reference to FIG. 2C) may receive a manifestrecord 200 from an electronic communication 250. The computing systemmay then update a project file (e.g., file database 280 discussed withreference to FIG. 2C) according to the structured text in the manifestrecord 200.

First, in step 410, the computing system receives the electroniccommunication. In some cases, the computing system may be monitoringincoming electronic communications, such as e-mail, in a particularelectronic environment. The computing system may detect which incominge-mails contain structured data, such as a manifest record, that may beautomatically read and executed in the computing system without need tointerpret unstructured text.

For example, in the case of a patent docketing system, a docketingsystem may monitor incoming e-mail and flag those with embedded manifestrecords received from a foreign agent.

Next, in step 420, the computing system saves a copy of the manifestrecord in a predetermined location. The computing system may optionallystore the manifest record in a local security environment. For example,the computing system may store the manifest record in a networkcontained within a firewall, or alternatively on a local drive orcomputer. The computing system may, for example, save a copy of themanifest record in a folder of a computer directory.

In some embodiments, the computing system may aggregate manifest recordspertaining to a single case, project, or file, in a single location forreference or to be read and analyzed in the production of futuremanifest records with a manifest record generating program.

In step 430, the computing system reads the manifest record to determinethe message type, the document type (if the electronic communicationcontains an applicable attachment), and associated deadlines. Themessage type may be, for example, an electronic communication conveyinga response from a patent office, a new action required by an applicant,a docketing task, a new deadline that must be met for a case, or areminder electronic communication. The document type may be, forexample, an office action, a filing receipt, or a communication from aforeign agent. The document type may be associated with the messagetype.

The computing system may additionally read structured text directed toother information in the manifest record, such as, for example, duedates, reminder dates, parties involved, actions required, reportinformation, event information, other attachments, associated actions orfollow-ups, or more.

Based on the deduced message and document types, the computing systemmay institute or execute an action by a computing program within acomputing or network system (step 440).

The action may be automated based on the information received from themanifest record. In some instances, the computing program mayadditionally extract unstructured text from the electronic communicationfor storage, analysis, or review.

For example, where an electronic communication from a foreign patentagent is received with an attached manifest record, the computing system(a docketing system here) would analyze the structured text of themanifest record. The structured text could indicate that the message isrelaying a recent search report issued by the foreign patent office. Thestructured text could additionally indicate that a response is duewithin six months of receipt of the search report. In this case, thecomputing system could record the deadline and schedule reminders forthe parties working on that case, in addition to notifying theinterested parties that a search report was received.

FIG. 5 is a flow chart depicting the use of the manifest recordgenerating program in a predictive manner in method 500. In someembodiments, the manifest record generating program may fetch priorcreated and saved manifest records to inform the creation of newmanifest records. In method 500, a manifest record generating program(e.g. manifest record creation system 100 discussed with reference toFIGS. 1 and 2A-2C) may create a manifest record 200 for sending with anelectronic communication 250 through an electronic communication system260. In method 500, the manifest record generating program functions ina predictive manner to allow easier updates to project files.

In this case, the manifest record generating program may read or detectmanifest records relevant to a specific case or file in a givendirectory. As shown in FIG. 5, the manifest record generating programfirst receives electronic communication information (step 510) andunstructured text (step 520), similar to the corresponding stepsdiscussed with reference to FIG. 3.

However, when the manifest record generating program is working basedoff aggregated manifest record(s), the manifest record generatingprogram then reviews the relevant historical manifest records (step530).

In some cases, the manifest record generating program may determine,based on the content of the aggregated manifest record(s), what the mostlikely next message type and document type should be. For example, in apatent docketing system, the manifest record generating program maydetermine, based on the aggregated manifest record(s), qualities such asupcoming due dates, typical response types and timelines that areupcoming, or which document(s) will be sent or received next. Thepotential message type and document type may be deduced from thisinformation.

The manifest record generating program may, based on the aggregatedmanifest record(s), produce a selection of options for the message typeand the document type based on the history of the case. For example,where a U.S. patent case has previously received a non-final officeaction and subsequent response, the manifest record generating programmay deduce that the next communication received from the patent officecould potentially be a final office action. Thus, the manifest recordgenerating program may display “final office action” for document typeas an option in a menu.

The manifest record generating program may then create the manifestrecord (step 540) once it has confirmed the document type and messagetype. Similar to the method described with reference to FIG. 3, themanifest record generating program would then attach the manifest recordand document to the electronic communication (steps 550, 560) and sendthe electronic communication (step 570).

Sample Embodiments

FIG. 6 is a flow chart showing a method 600 of the manifest recordgenerating program creating a manifest record for an outsideorganization action, for example, for reporting actions taken by apatent office, government organization, or other entity outside thebusiness. For example, where an action by a patent office is received byan attorney's office, the attorney's team may use the manifest recordgenerating program to create a manifest record depicting the actiontype, required response, and due date of that response, to send out withan electronic communication to a client or to a corresponding foreignagent, or internally within the attorney's office.

In method 600, the manifest record generating program determines theaction taken by the patent office (or other outside organization) (608).The manifest record generating program may determine the action byshowing a display and receiving a selection from pre-determined list ofactions. In some examples, the pre-determined list of actions may be adrop-down menu or other user interface. For example, in a patent office,the action may be the issuance of an office action or search report, afiling receipt, a notice of abandonment, a notice of allowance, or otheritems.

The manifest record generating program may determine the message typebased on the action taken by the outside party (e.g., based on an actiontaken by the relevant patent office) (610). The manifest recordgenerating program may deduce, based on the type of action taken, whatmessage type to associate with the electronic communication for themanifest record. For example, the message type may be a report out of areceived office action.

Once the manifest record generating program determines the action takenby the patent office and the message type, the manifest recordgenerating program may record the date the action was taken, ifapplicable (612). In this case, the manifest record generating programmay receive and record date information from a field in the userinterface. The date may be, for example, the date the patent officeacted, the date the patent office mailed a notice, or the date thenotice was received.

Subsequently, the manifest record generating program may record whethera response is required to the action of the patent office (614). Themanifest record generating program may receive information on date andwhether a response is required through the user interface display. Forexample, if an office action is received from a patent office, themanifest record generating program may record that an amendment or otherresponse may be required. This may be done, for example, by the manifestrecord generating program showing a display requesting whether aresponse is required and receiving input.

If a response is required, the manifest record generating program mayprompt the user to insert a due date for the response by showing adisplay (616). After receiving the due date, the manifest recordgenerating program may determine whether another action has beenreceived or is required (617). If another action is required, themanifest record generating program will cycle back to the beginning anddetermine the corresponding patent office action.

If a response is not required to the original action, the manifestrecord generating program may skip recording a due date, and insteaddetermine whether another action is has been received or is required byproducing a display asking whether another action is required. Ifanother action is required (615), the manifest record generating programwill cycle back to the beginning and determine the corresponding patentoffice action.

Once all related actions by the patent office and required response anddue dates have been determined and cataloged by the manifest recordgenerating program to ensure association of the correct message type,the manifest record generating program may receive and attach documents(618, 619). The manifest record generating program may, for example,produce a document retrieval display and receive the document through amenu such as a drag and drop menu.

The manifest record generating program may then associate a documenttype based on the attached document(s)(620). The manifest recordgenerating program may take the message type, document type, and otherdue date information, and create the manifest record. The manifestrecord may then be attached to the electronic communication by themanifest record generating program (622). If there are no documents toattach, the manifest record generating program may skip the associationof document type and simply create a manifest record based on themessage type.

Once the manifest record is attached to the electronic communication,the manifest record generating program may produce a review screendisplay (623, 624). When the manifest record generating program receivesconfirmation and submission of the electronic communication withattached manifest record and documents, the manifest record generatingprogram may provide a summary report (626).

For example, if the manifest record generating program is reporting asearch report received from a patent office, the manifest recordgenerating program may categorize the patent office action as a searchreport, record the appropriate response date, and produce associatedmessage type in the structured text based on the received search report.The manifest record generating program may then receive and attach thesearch report document to the electronic communication and associate theappropriate document type in the structured text.

The manifest record generating program may take the associatedstructured text, including the message type and document type, to createa manifest record containing structured data encoding the message type,document type, and potentially other structured text, such as due datesor associated parties. The manifest record generating program may attachthe manifest record to the electronic communication, along with thedocument search report, and subsequently allow for review and sending ofthe electronic communication with the manifest record.

FIG. 7 is a flow chart of the manifest record generating programcreating a manifest record for an internal action reporting to theoutside organization. For example, method 700 could include, but is notlimited to, reporting of filing an amendment or response in a patentoffice, reporting of filing a motion or brief in court, or reporting ofsending instructions to other counsel. Specifically, a law office coulduse the manifest record generating program to create a manifest recorddepicting the type of action taken by the law office and anycorresponding date and include that manifest record with an electroniccommunication to the client.

First, the manifest record generating program determines what action wastaken by the internal organization (710). The manifest record generatingprogram may display, for example, a drop-down list of actions that theinternal organization could take or has taken.

Next, the manifest record generating program may record the date actionwas taken (712). The manifest record generating program may display atext field or a calendar field to receive the date action was taken.

Based on the action that was taken, the manifest record generatingprogram may associate a message type with the action and electroniccommunication (714). If the action is, for example, filing of a patentapplication in a patent office, either in the U.S. or internationally,the manifest record generating program may show a display specific tothe action of filing a patent application.

For example, if the message type is reporting of filing of a patentapplication, the manifest record generating program may then show adisplay confirming whether formalities are required for that patentapplication (716). If the manifest record generating program receives a“yes” answer to this display, the manifest record generating program maythen display the appropriate formality fields to be filled (718).

Subsequently, the manifest record generating program may show a displayrequesting whether there is another action that was taken and should beincluded with this particular electronic communication (720). If theanswer received is “yes,” the manifest record generating program maydisplay the first field (710) again, to determine the action type andmessage type.

Once the manifest record generating program has gathered sufficientinformation on the actions taken by the internal organization, such aswhether the action was filing of a patent application and the associatedformalities, and associated a message type with the particularelectronic communication, the manifest record generating program maydetermine whether documents will be attached to the electroniccommunication.

The manifest record generating program may display a field requestingwhether documents will be attached (722). If documents will be attached,the manifest record generating program may display a field for receivingdocuments, such as a drag-and-drop field. Based on the documentsreceived, the manifest record generating program may associate adocument type (724).

Using the associated message type and document type, the manifest recordgenerating program may build a manifest record (726, see also FIGS.2A-2B). The manifest record may be, for example, structured text (e.g.,.CSV or excel file) containing information regarding the message type,document type, and other associated structured text such as due dates.The manifest record generating program may then attach the manifestrecord to the electronic communication (728).

After attachment of the manifest record, the manifest record generatingprogram may show a review display, with an option (e.g., a button) tosubmit the electronic communication with attached manifest record (730).The manifest record generating program may then send the electroniccommunication.

After submission, the manifest record generating program may then createa summary report for review by a user (732). This summary may bepresented on a display by the manifest record generating program, sentto the user by the manifest record via electronic communication, orsaved as a file in the local computer environment.

FIG. 8 is a flow chart of the manifest record generating programcreating a manifest record for an action by a third party, such as, forexample, a foreign agent. For example, the foreign agent may use themanifest record generating program to create a manifest record thatspecifies the most recent action by a foreign patent office, includingthe due date, to include with an electronic communication to a U.S.attorney working on the corresponding case.

The manifest record generating program may first determine the actionbeing taken (806) and the associated message type (808). In this case,an electronic communication may be sent to or received from the foreignagent that includes an attached or imbedded manifest record. The messagetype may be, for example, reporting filing or publication of a foreignpatent application, reporting of a search report received, an oppositionor reexam, or reporting of abandonment or issuance.

Then, the manifest record generating program may determine whether thereis an upcoming due date by displaying the question for a user andreceiving a yes or no response (810). If the manifest record receives a“yes” response and there is a due date associated with the electroniccommunication, the manifest record generating program may display a textfield or calendar field to receive the due date (812). For example, ifthe foreign agent is sending along a search report, a due date forresponse to that search report may be entered in step 812.

The manifest record generating program may subsequently show a displayasking whether document(s) will be attached to the electroniccommunication (814). (If there is no associated due date, the manifestrecord generating program may skip to this step 814). If the manifestrecord generating program receives a positive response (“yes”), themanifest record generating program may show a display for receiving thedocument(s) and any accompanying reminders (816). For example, a foreignsearch report, or a response/amendment written by the foreign agent maybe attached to the electronic communication at this stage.

At step 816, the manifest record generating program may record thedocument type associated with the attached document(s). After themanifest record generating program has determined and recorded all duedates and document types, the manifest record generating program maycreate the manifest record.

The manifest record generating program may take the determined messagetype (from step 808) and determined document type (from step 816) andcreate the manifest record to be included with the electroniccommunication (818) and attach it to or embed it in the electroniccommunication (820).

After attachment of the manifest record, the manifest record generatingprogram may show a review display, with an option (e.g., a button) tosubmit the electronic communication with attached manifest record (822).The manifest record generating program may then send the electroniccommunication.

After submission, the manifest record generating program may then createa summary report for review by a user (824). This summary may bepresented on a display by the manifest record generating program, sentto the user by the manifest record via electronic communication, orsaved as a file in the local computer environment.

FIG. 9 is a flow chart of the manifest record generating programcreating a manifest record for an internal action reporting to a thirdparty, such as an internal person reporting to a foreign agent. Forexample, where a U.S. attorney writes instructions for a foreign agentin the corresponding case, the manifest record generating program maycreate a manifest record specifying the action taken by the U.S.attorney and the appropriate due dates.

In method 900, the manifest record generating program first determinesthe action being taken and the associated message type (910, 912). Inthis case, that could include, for example, instructions written by theU.S. attorney.

Subsequently, the manifest record generating program may show a displayinquiring whether a response is required to the action and electroniccommunication. (914) If the manifest record generating program receivesan affirmative response (“yes”), the manifest record generating programmay display a text or calendar field for the appropriate due date andrecord that due date (916).

After receiving the due date, the manifest record generating program mayshow a display asking if there is another request to be added (918). Ifthe manifest record generating program receives an affirmative response(“yes”), the manifest record generating program may cycle back to thefirst display to determine the action being taken and the message typeassociated with the second request (910, 912).

If there is not a second request, the manifest record generating programmay show a display asking whether document(s) will be attached (920). If“yes,” the manifest record generating program may then display adocument receiving field (e.g., a drag and drop field), and receive thedocuments (922). The manifest record generating program may thenassociate a document type with those document(s).

Once all the appropriate requests have been recorded, along with thecorresponding due dates (or in the instance where a response is notrequired an there is no associated due date) and documents, the manifestrecord generating program may produce the manifest record based on theassociated message type and document type (924) and attach the manifestrecord (926).

After attachment of the manifest record, the manifest record generatingprogram may show a review display, with an option (e.g., a button) tosubmit the electronic communication with attached manifest record (928).The manifest record generating program may then send the electroniccommunication.

After submission, the manifest record generating program may then createa summary report for review by a user (930). This summary may bepresented on a display by the manifest record generating program, sentto the user by the manifest record via electronic communication, orsaved as a file in the local computer environment.

FIG. 10 is a schematic of the user interface 1000 of the manifest recordgenerating program. The user interface 1000 may include, for example, afield for the type of action (1010), a field for due date (1012), and afield for document reception (1014), among other fields forbibliographic data. User interface 1000 may be the user interface for amanifest record creation system such as system 100 discussed withreference to FIGS. 1, 2A-2C above. Interaction with user interface 1000may allow for the manifest record generating program to create amanifest record 200 according to user inputs.

The type of action field 1010 may be, for example, a drop-down menu witha pre-selected list of potential actions. These may include, forexample, report outs of outside organization (e.g., patent officeactions) such as filing receipts, search reports, office actions,advisory actions, notices of allowance, notices of abandonment, or otheractions. The list may alternatively or additionally include actionsrelated to foreign agents, such as reports of actions done by foreignoffices, reports of filing application or amendments, or otherreminders.

The manifest record generating program may let the due date field 1012appear or disappear depending on the action selected in the initialfield 1010. If the action has an associated due date, the manifestrecord generating program may present the due date field as an open textfield or as a calendar field.

The document reception field 1014 may be, for example, a drag-and-dropfield where a user may insert various documents. The document receptionfield 1014 may have a variable number of slots depending on the actionchosen in the initial field 1010. For example, if a report out of anissued office action is selected in field 1010, then field 1014 maychange to allow for attachment of one document titled “office action.”

Computer Embodiment

FIG. 11 is a block diagram of a typical, general-purpose computer 1100that may be programmed into a special purpose computer suitable forimplementing one or more embodiments of the manifest record generatingprogram disclosed herein. The manifest record generating programdescribed above may be implemented on any general-purpose processingcomponent, such as a computer with sufficient processing power, memoryresources, and communications throughput capability to handle thenecessary workload placed upon it. The computer 1100 includes aprocessor 1102 (which may be referred to as a central processor unit orCPU) that is in communication with memory devices including secondarystorage 1104, read only memory (ROM) 1106, random access memory (RAM)1108, input/output (I/O) devices 1110, and network connectivity devices1112. The processor 1102 may be implemented as one or more CPU chips ormay be part of one or more application specific integrated circuits(ASICs).

The secondary storage 1104 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 1108 is not large enough tohold all working data. Secondary storage 1104 may be used to storeprograms that are loaded into RAM 1108 when such programs are selectedfor execution. The ROM 1106 is used to store instructions and perhapsdata that are read during program execution. ROM 1106 is a non-volatilememory device that typically has a small memory capacity relative to thelarger memory capacity of secondary storage 1104. The RAM 1108 is usedto store volatile data and perhaps to store instructions. Access to bothROM 1106 and RAM 1108 is typically faster than to secondary storage1104.

The devices described herein may be configured to includecomputer-readable non-transitory media storing computer readableinstructions and one or more processors coupled to the memory, and whenexecuting the computer readable instructions configure the computer 1100to perform method steps and operations described above with reference toFIG. 3 to FIG. 9. The computer-readable non-transitory media includesall types of computer readable media, including magnetic storage media,optical storage media, flash media and solid-state storage media.

It should be further understood that software including one or morecomputer-executable instructions that facilitate processing andoperations as described above with reference to any one or all of stepsof the disclosure may be installed in and sold with one or more serversand/or one or more routers and/or one or more devices within consumerand/or producer domains consistent with the disclosure. Alternatively,the software may be obtained and loaded into one or more servers and/orone or more routers and/or one or more devices within consumer and/orproducer domains consistent with the disclosure, including obtaining thesoftware through physical medium or distribution system, including, forexample, from a server owned by the software creator or from a servernot owned but used by the software creator. The software may be storedon a server for distribution over the Internet, for example.

Also, it will be understood by one skilled in the art that thisdisclosure is not limited in its application to the details ofconstruction and the arrangement of components set forth in thedescription or illustrated in the drawings. The embodiments herein arecapable of other embodiments, and capable of being practiced or carriedout in various ways. Also, it will be understood that the phraseologyand terminology used herein is for the purpose of description and shouldnot be regarded as limiting. The use of “including,” “comprising,” or“having” and variations thereof herein is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional items.Unless limited otherwise, the terms “connected,” “coupled,” and“mounted,” and variations thereof herein are used broadly and encompassdirect and indirect connections, couplings, and mountings. In addition,the terms “connected” and “coupled” and variations thereof are notrestricted to physical or mechanical connections or couplings. Further,terms such as up, down, bottom, and top are relative, and are employedto aid illustration, but are not limiting.

The components of the illustrative devices, systems and methods employedin accordance with the illustrated embodiments may be implemented, atleast in part, in digital electronic circuitry, analog electroniccircuitry, or in computer hardware, firmware, software, or incombinations of them. These components may be implemented, for example,as a computing program product such as a computing program, program codeor computer instructions tangibly embodied in an information carrier, orin a machine-readable storage device, for execution by, or to controlthe operation of, data processing apparatus such as a programmableprocessor, a computer, or multiple computers.

A computing program may be written in any form of programming language,including compiled or interpreted languages, and it may be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputing program may be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a communication network. Also, functional programs,codes, and code segments for accomplishing the techniques describedherein may be easily construed as within the scope of the presentdisclosure by programmers skilled in the art. Method steps associatedwith the illustrative embodiments may be performed by one or moreprogrammable processors executing a computing program, code orinstructions to perform functions (e.g., by operating on input dataand/or generating an output). Method steps may also be performed by, andapparatus may be implemented as, special purpose logic circuitry, e.g.,an FPGA (field programmable gate array) or an ASIC (application-specificintegrated circuit), for example.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general-purpose processor, a digital signalprocessor (DSP), an ASIC, a FPGA or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

Processors suitable for the execution of a computing program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random-access memory or both. The essential elements of a computer area processor for executing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto-optical disks, or optical disks. Information carrierssuitable for embodying computing program instructions and data includeall forms of non-volatile memory, including by way of example,semiconductor memory devices, e.g., electrically programmable read-onlymemory or ROM (EPROM), electrically erasable programmable ROM (EEPROM),flash memory devices, and data storage disks (e.g., magnetic disks,internal hard disks, or removable disks, magneto-optical disks, andCD-ROM and DVD-ROM disks). The processor and the memory may besupplemented by or incorporated in special purpose logic circuitry.

Those of skill in the art understand that information and signals may berepresented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill in the art further appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the disclosure. A software module may residein random access memory (RAM), flash memory, ROM, EPROM, EEPROM,registers, hard disk, a removable disk, a CD-ROM, or any other form ofstorage medium known in the art. An exemplary storage medium is coupledto the processor such the processor may read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor. In other words, the processorand the storage medium may reside in an integrated circuit or beimplemented as discrete components.

As used herein, “machine-readable medium” means a device able to storeinstructions and data temporarily or permanently and may include, but isnot limited to, random-access memory (RAM), read-only memory (ROM),buffer memory, flash memory, optical media, magnetic media, cachememory, other types of storage (e.g., Erasable Programmable Read-OnlyMemory (EEPROM)), and/or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store processor instructions. Theterm “machine-readable medium” shall also be taken to include anymedium, or combination of multiple media, that is capable of storinginstructions for execution by one or more processors, such that theinstructions, when executed by one or more processors cause the one ormore processors to perform any one or more of the methodologiesdescribed herein. Accordingly, a “machine-readable medium” refers to asingle storage apparatus or device, as well as “cloud-based” storagesystems or storage networks that include multiple storage apparatus ordevices. The term “machine-readable medium” as used herein excludessignals per se.

Notes and Examples

The following, non-limiting examples, detail certain aspects of thepresent subject matter to solve the challenges and provide the benefitsdiscussed herein, among others.

Example 1 includes a method of creating a manifest record for anoutgoing electronic communication including receiving a messagecomprising unstructured text to be inserted into the outgoing electroniccommunication, generating a manifest record for attachment to theoutgoing electronic communication using a web browser executing anapplication downloaded from a server remote from the client computer,the manifest record comprising structured data specifying a messagetype, wherein generating the manifest record comprises the applicationreceiving a selection of a message type from a first menu comprising aplurality of choices for the message type and producing structured databased on the selection, outputting the manifest record and saving themanifest record to the client computer, attaching the manifest record tothe outgoing electronic communication, and sending the outgoingelectronic communication with the manifest record.

Example 2 includes Example 1, wherein the manifest record indicates anaction to be executed by an automated electronic system upon receipt ofthe electronic communication.

Example 3 includes any of Examples 1-2, wherein displaying the firstmenu comprises displaying a drop-down menu, drag and drop fields, orpop-up menu.

Example 4 includes any of Examples 1-3, wherein the structured dataspecifies the message type.

Example 5 includes any of Examples 1-4, further including identifying atleast one document to be sent with the outgoing electroniccommunication.

Example 6 includes any of Examples 1-5, wherein the manifest recordfurther comprises structured data specifying a document type associatedwith the at least one document.

Example 7 includes any of Examples 1-6, wherein generating the manifestrecord further comprises assigning the document type associated with theat least one document.

Example 8 includes any of Examples 1-7, wherein assigning the documenttype associated with the at least one document comprises displaying asecond menu including a plurality of choices for the document type,receiving a selection from the second menu, and producing structureddata based on the selection.

Example 9 includes any of Examples 1-8, further including changing theplurality of choices for the document type in the second menu dependingon the message type.

Example 10 includes any of Examples 1-9, wherein displaying the secondmenu comprises displaying a choice of document type including one of aplurality of forms or one of a plurality of written communication types.

Example 11 includes any of Examples 1-10, further including storing themanifest record in a local security environment.

Example 12 includes any of Examples 1-11, wherein storing the manifestrecord in a local security environment including storing the manifestrecord in a network having a firewall.

Example 13 includes any of Examples 1-12, wherein storing the manifestrecord comprises placing the manifest record in a folder in a computerdirectory.

Example 14 includes any of Examples 1-13, wherein generating themanifest record comprises generating a word processing document, a textfile, a comma separated values file, or a rich text file.

Example 15 includes any of Examples 1-14, wherein generating themanifest record further comprises generating structured text describingdocument type, due date, report information, event information,electronic communication purpose, attachments, or combinations thereof.

Example 16 includes any of Examples 1-15, further including fetchingprior manifest records to inform the creation of new manifest records.

Example 17 includes any of Examples 1-16, further including: aggregatingmanifest records to produce aggregated manifest records, analyzing theaggregated manifest records, and executing an action in a computingsystem based on the analyzing the aggregated manifest records.

Example 18 includes any of Examples 1-17, further including: reading oneor more manifest records, analyzing the one or more manifest records todetermine document types and/or message types specified in the manifestrecords, and dynamically determining one or more menu selections todisplay based on the one or more manifest records.

Example 19 includes a method comprising receiving an electroniccommunication having unstructured text in a body of the electroniccommunication and a manifest record that specifies a message typeassociated with the electronic communication, saving a copy of themanifest record, reading the manifest record to determine the messagetype, and executing an action in an electronic system automaticallybased on the manifest record.

Example 20 includes Example 19, wherein the electronic communicationfurther comprises a document attached to the electronic communication.

Example 21 includes any of Examples 19-20, further including saving acopy of the document, and reading the manifest record to determine thedocument type.

Example 22 includes any of Examples 19-21, wherein saving the copy ofthe manifest record comprises saving the manifest record in a localsecurity environment including a network with a firewall.

Example 23 includes any of Examples 19-22, wherein reading the manifestrecord comprises automated interpretation of the structured text in themanifest record.

Example 24 includes any of Examples 19-23, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises matching the manifest record to one or more stored templatesand executing one or more actions based on those templates.

Example 25 includes any of Examples 19-24, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises moving one or more files within a database to one or morespecified locations.

Example 26 includes any of Examples 19-25, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises adding the message to a database.

Example 27 includes any of Examples 19-26, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises updating a database.

Example 28 includes any of Examples 19-27, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises sending a new electronic communication.

Example 29 includes any of Examples 19-28, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises launching a computer program or application.

Example 30 includes any of Examples 19-29, wherein executing an actionin an electronic system automatically based on the manifest recordcomprises scheduling a deadline for a one or more projects.

Example 31 includes a non-transitory computer-readable medium thatstores instructions that when executed by one or more processors causethe one or more processors to perform operations including receiving amessage including unstructured text to be inserted into an outgoingelectronic communication, generating a manifest record for attachment tothe outgoing electronic communication, the manifest record includingstructured data specifying a message type, wherein generating themanifest record comprises assigning the message type associated with themessage to the manifest record, attaching the manifest record to theoutgoing electronic communication, and sending the outgoing electroniccommunication with the manifest record attached.

Example 32 includes Example 31 wherein manifest record indicates aresponsive action to be taken by a file management system upon receiptof the electronic communication.

Example 33 includes any of Examples 31-32, further includinginstructions that when executed by the one or more processors cause theone or more processors to attach a document to the electroniccommunication.

Example 34 includes any of Examples 31-33, wherein the structured datafurther comprises one or more deadlines.

Example 35 includes any of Examples 31-34, wherein the structured datafurther comprises report information, event information, electroniccommunication purpose, attachments, or combinations thereof.

Example 36 includes any of Examples 31-35, further includinginstructions that when executed by the one or more processors cause theone or more processors to store the manifest record in a local securityenvironment.

Example 37 includes a non-transitory computer-readable medium thatstores instructions that when executed by one or more processors causethe one or more processors to perform operations including receiving anelectronic communication having unstructured text in a body of theelectronic communication and a manifest record specifying a message typeassociated with the electronic communication, saving a copy of themanifest record, reading the manifest record to determine the messagetype, and executing an action in an electronic system automaticallybased on the manifest record.

Example 38 includes Example 37, wherein the manifest record comprisesstructured data.

Example 39 includes any of Examples 37-38, wherein the electroniccommunication further comprises a document attached to the electroniccommunication.

Example 40 includes any of Examples 37-39, wherein the manifest recordfurther specifies a document type associated with the document.

Example 41 includes any of Examples 37-40, further includinginstructions that when executed by the one or more processors cause theone or more processors to read the manifest record to determine thedocument type.

Example 42 includes any of Examples 37-41, further includinginstructions that when executed by the one or more processors cause theone or more processors to execute an action in an electronic systemautomatically based on the document type.

Example 43 includes any of Examples 37-42, further includinginstructions that when executed by the one or more processors cause theone or more processors to save a copy of the document.

Example 44 includes a system having a manifest record creation systemthat creates a manifest record including structured text describing anaction to be executed by a computing machine upon receipt of anassociated electronic communication, and an electronic communicationsystem that produces an electronic communication, attaches the manifestrecord to the electronic communication, and sends the electroniccommunication to a recipient.

Example 45 includes Example 44, further including one or more sources ofdata configured to input data or documents into the manifest recordcreation system.

Example 46 includes any of Examples 44-45, wherein the manifest recordcreation system comprises a computer program with a user interface forinput of data and documents.

Example 47 includes a system having an electronic communication systemthat receives an electronic communication with manifest record attached,the manifest record including structured test describing an action to betaken upon receipt of the electronic communication, and an automateddocketing system that interprets the structured text in the manifestrecord and executes the action.

Example 48 includes Example 47, wherein the automated docketing systemis fully automated.

Example 49 includes any of Examples 47-48, wherein the automateddocketing system is partially automated.

Example 50 includes any of Examples 47-49, further including a databaseconfigured to receive the action executed by the automated docketingsystem.

The above detailed description includes references to the accompanyingdrawings, which form a part of the detailed description. The drawingsshow, by way of illustration, specific embodiments in which theinvention may be practiced. These embodiments are also referred toherein as “examples.” Such examples may include elements in addition tothose shown or described. However, the present inventors alsocontemplate examples in which only those elements shown or described areprovided. Moreover, the present inventors also contemplate examplesusing any combination or permutation of those elements shown ordescribed (or one or more aspects thereof), either with respect to aparticular example (or one or more aspects thereof), or with respect toother examples (or one or more aspects thereof) shown or describedherein.

In the event of inconsistent usages between this document and anydocuments so incorporated by reference, the usage in this documentcontrols.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, device,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments may be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is provided to complywith 37 C.F.R. § 1.72(b), to allow the reader to quickly ascertain thenature of the technical disclosure. It is submitted with theunderstanding that it will not be used to interpret or limit the scopeor meaning of the claims. Also, in the above Detailed Description,various features may be grouped together to streamline the disclosure.This should not be interpreted as intending that an unclaimed disclosedfeature is essential to any claim. Rather, inventive subject matter maylie in less than all features of a particular disclosed embodiment.Thus, the following claims are hereby incorporated into the DetailedDescription as examples or embodiments, with each claim standing on itsown as a separate embodiment, and it is contemplated that suchembodiments may be combined with each other in various combinations orpermutations. The scope of the invention should be determined withreference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

1. A method of creating a manifest record for an outgoing electroniccommunication on a client computer, comprising: receiving a messagecomprising unstructured text to be inserted into the outgoing electroniccommunication; generating a manifest record for attachment to theoutgoing electronic communication using a web browser executing anapplication downloaded from a server remote from the client computer,the manifest record comprising structured data specifying a messagetype, wherein generating the manifest record comprises the applicationreceiving a selection of a message type from a first menu comprising aplurality of choices for the message type and producing structured databased on the selection; the application outputting the manifest recordand saving the manifest record to the client computer; attaching themanifest record to the outgoing electronic communication; and sendingthe outgoing electronic communication with the manifest record.
 2. Themethod of claim 1, wherein the manifest record indicates an action to beexecuted by an automated electronic system upon receipt of theelectronic communication.
 3. The method of claim 1, wherein thestructured data specifies the message type.
 4. The method of claim 1,further comprising identifying at least one document to be sent with theoutgoing electronic communication, and wherein the manifest recordfurther comprises structured data specifying a document type associatedwith the at least one document.
 5. The method of claim 4, whereingenerating the manifest record further comprises assigning the documenttype associated with the at least one document, and wherein assigningthe document type associated with the at least one document comprisesdisplaying a second menu comprising a plurality of choices for thedocument type, receiving a selection from the second menu, and producingstructured data based on the selection.
 6. The method of claim 1,further comprising storing the manifest record in a local securityenvironment.
 7. The method of claim 1, wherein generating the manifestrecord further comprises generating structured text describing documenttype, due date, report information, event information, electroniccommunication purpose, attachments, or combinations thereof.
 8. Themethod of claim 1, further comprising fetching prior manifest records toinform the creation of new manifest records.
 9. The method of claim 1,further comprising: aggregating manifest records to produce aggregatedmanifest records; analyzing the aggregated manifest records; andexecuting an action in a computing system based on the analyzing theaggregated manifest records.
 10. The method of claim 1, furthercomprising: reading one or more manifest records; analyzing the one ormore manifest records to determine document types and/or message typesspecified in the manifest records; and dynamically determining one ormore menu selections to display based on the one or more manifestrecords.
 11. A method comprising: receiving an electronic communicationcomprising: unstructured text in a body of the electronic communication;and a manifest record that specifies a message type associated with theelectronic communication; saving a copy of the manifest record; readingthe manifest record to determine the message type; and executing anaction in an electronic system automatically based on the manifestrecord.
 12. The method of claim 11, wherein the electronic communicationfurther comprises a document attached to the electronic communication.13. The method of claim 12, further comprising saving a copy of thedocument, and reading the manifest record to determine a document type.14. The method of claim 11, wherein reading the manifest recordcomprises automated interpretation of structured text in the manifestrecord.
 15. The method of claim 11, wherein executing an action in anelectronic system automatically based on the manifest record comprisesat least one of: matching the manifest record to one or more storedtemplates and executing one or more actions based on those templates;moving one or more files within a database to one or more specifiedlocations; adding the message to a database; updating a database;sending a new electronic communication; launching a computer program orapplication; scheduling a deadline for a one or more projects; andcombinations thereof. 16-17. (canceled)
 18. A system comprising: anelectronic communication system that receives an electroniccommunication with manifest record attached, the manifest recordcomprising structured test describing an action to be taken upon receiptof the electronic communication; and an automated docketing system thatinterprets structured text in the manifest record and executes theaction.
 19. The system of claim 18, wherein the automated docketingsystem is fully or partially automated.
 20. The system of claim 18,further comprising a database configured to receive the action executedby the automated docketing system.